Available ProtectToolkit 7 components
This topic lists all of the ProtectToolkit 7 components that are available to install on each supported platform along with the prerequisites for each component. For installation procedures, refer to the following sections:
This section lists ProtectToolkit 7 components that are available to install on Windows along with the prerequisites for each component.
- ProtectToolkit Client
-
Installs the ProtectToolkit-C Runtime, which includes all the necessary tools and interfaces for a ProtectToolkit-C Cryptoki service provider.
- ProtectToolkit SDK
-
Installs the ProtectToolkit-C software development platform. Header files are included, in addition to the ProtectToolkit-C Runtime.
- ProtectToolkit FM SDK
-
Installs the functionality module (FM) development kit. Install this component if you plan to develop FMs to add custom functionality to the ProtectServer 3 HSM.
Prerequisites: ProtectToolkit SDK
Note
Thales recommends that you develop and test FMs in Software Emulation mode before installing them on your production HSMs. For more information about this mode, refer to Operating modes.
- ProtectToolkit Java Runtime
-
Installs all the necessary tools and interfaces for a ProtectToolkit-J Cryptoki service provider, using the Java Cryptographic Architecture (JCA)/Java Cryptographic Extension (JCE) interface.
Prerequisites: ProtectToolkit Client
- ProtectToolkit Java SDK
-
Installs the ProtectToolkit-J software development platform, for developing Java applications for use with your ProtectServer 3 HSM.
Prerequisites: SafeNet ProtectToolkit Java Runtime
- HSM Communication Interface
-
Installs components that allow ProtectToolkit to communicate with a ProtectServer 3 HSM. If you plan to use ProtectToolkit in Software Emulation mode only, you can clear this option.
-
Network: Select this option if you are connecting to a ProtectServer 3 HSM over a network.
-
PCI: Installs the drivers for a locally-installed ProtectServer 3 PCIe.
- HSM Net Server: Select this option if you plan to allow other ProtectToolkit clients to access your locally-installed ProtectServer 3 PCIe over a network.
-
- Microsoft Cryptographic Provider
-
Installs the necessary tools and interfaces tor a ProtectToolkit-M Cryptoki service provider, using Microsoft's cryptographic API.
Prerequisites: ProtectToolkit Client
-
CNG Provider: Installs components for using ProtectToolkit-M with Microsoft's updated Cryptography Next Generation API (CNG).
-
ProtectToolkit M Provider: Installs components for using ProtectToolkit-M with the older Microsoft Cryptographic API (MSCAPI).
-
This section lists ProtectToolkit 7 components that are available to install on Linux platforms along with the prerequisites for each component.
Note
Components are listed below in the ideal installation order.
Only install the components required for your deployment.
Installation package subdirectories and package names are listed for users that are attempting to install components manually; -x.x.x-yy
in the installation package name refers to the ProtectToolkit version number and varies by ProtectToolkit 7 version downloaded from the Thales Customer Support Portal.
- SafeNet Network HSM Access Provider
-
Installs the components required to access a ProtectServer 3 HSM over the network, whether a ProtectServer 3 External, ProtectServer 3+ External, or ProtectServer 3 PCIe configured for network access.
-
Package name: PTKnethsm-x.x.x-yy.x86_64.rpm
-
Package subdirectory: /output-unix/Linux64/network_hsm_access_provider
-
- SafeNet ProtectServer PCIe HSM Access Provider (K7) - device driver
-
Installs the device driver components for a ProtectServer 3 PCIe HSM installed in the host system.
-
Package name: PTKpcihsmK7-x.x.x-yy.x86_64.rpm
-
Package subdirectory: /output-unix/Linux64/pci_hsm_access_provider_PSI
-
- SafeNet HSM Net Server
-
Installs the components required to make an installed ProtectServer 3 PCIe HSM available on the network to other ProtectToolkit clients.
-
Prerequisites: an installed ProtectServer 3 PCIe and SafeNet ProtectServer PCIe HSM Access Provider (K7) - device driver.
-
Package name: PTKnetsrv-x.x.x-yy.x86_64.rpm
-
Package subdirectory: /output-unix/Linux64/hsm_net_server
-
- SafeNet ProtectToolkit C Runtime
-
Installs the necessary tools and interfaces for a ProtectToolkit-C based Cryptoki service provider.
-
Prerequisites: The Access Provider package relevant to your deployment. Refer to the descriptions above.
-
Package name: PTKcprt-x.x.x-yy.x86_64.rpm
-
Package subdirectory: /output-unix/Linux64/PTKC_Runtime
-
- SafeNet ProtectToolkit C SDK
-
Installs the ProtectToolkit-C software development platform. Header files are included, in addition to the ProtectToolkit-C Runtime.
-
Prerequisites: The Access Provider package relevant to your deployment. Refer to the descriptions above.
-
Package name: PTKcpsdk-x.x.x-yy.x86_64.rpm
-
Package subdirectory: /output-unix/Linux64/hsm_net_server
Note
SafeNet ProtectToolkit C Runtime and SafeNet ProtectToolkit C SDK cannot be installed at the same time. To switch between them, first uninstall the package you no longer wish to use.
-
- SafeNet ProtectToolkit Java Runtime
-
Installs necessary tools and interfaces for a ProtectToolkit-J Cryptoki service provider, using the Java Cryptographic Architecture (JCA)/Java Cryptographic Extension (JCE) interface.
-
Prerequisites: SafeNet ProtectToolkit C Runtime
-
Package name: PTKjprov-x.x.x-yy.x86_64.rpm
-
Package subdirectory: /output-unix/Linux64/PTKJ_Runtime
-
- SafeNet ProtectToolkit Java SDK
-
Installs the ProtectToolkit-J software development platform used to develop Java applications for use with your ProtectServer 3 HSM.
-
Prerequisites: SafeNet ProtectToolkit Java Runtime
-
Package name: PTKjpsdk-x.x.x-yy.x86_64.rpm
-
Package subdirectory: /output-unix/Linux64/PTKJ_SDK
-
- SafeNet ProtectToolkit FM SDK
-
Installs the ProtectToolkit functionality module software development kit (SDK) for building FMs or host applications.
-
Prerequisites: SafeNet ProtectToolkit C SDK and Embedded Linux Development Kit (ELDK)
-
Package name: PTKfmsdk-x.x.x-yy.x86_64.rpm
-
Package subdirectory: /output-unix/Linux64/fm_sdk
Note
SafeNet ProtectToolkit C Runtime and SafeNet ProtectToolkit FM SDK cannot be installed on the same machine. Thales recommends FM development on a separate machine.
-
- Embedded Linux Development Kit (ELDK)
-
Installs the components required to compile and run your functionality modules.
-
Prerequisites: SafeNet ProtectToolkit C SDK and SafeNet ProtectToolkit FM SDK.
-
Package name: eldk-x.x.x.i686.rpm
-
Package subdirectory: /output-unix/Linux64/fm_toolchain
-
This section lists ProtectToolkit 7 components that are available to install on AIX along with the prerequisites for each component.
Note
Components are listed below in the ideal installation order.
Only install the components required for your deployment.
Installation package subdirectories and package names are listed for users that are attempting to install components manually; -x.x.x-yy
in the installation package name refers to the ProtectToolkit version number and varies by ProtectToolkit 7 version downloaded from the Thales Customer Support Portal.
- SafeNet Network HSM Access Provider
-
Installs the components required to access a ProtectServer 3 HSM over the network, whether a ProtectServer 3 External, ProtectServer 3+ External, or ProtectServer 3 PCIe configured for network access.
-
Package name: PTKnethsm.rte
-
Package subdirectory: /output-unix/AIX/PTKnethsm
-
- ProtectToolkit C Runtime
-
Installs all the necessary tools and interfaces for a ProtectToolkit-C based Cryptoki service provider.
-
Prerequisites: SafeNet Network HSM Access Provider
-
Package name: PTKcprt.rte
-
Package subdirectory: /output-unix/AIX/PTKcprt
-
- ProtectToolkit C SDK
-
Installs the PTK-C software development platform. Header files are included, in addition to the PTK-C Runtime.
-
Prerequisites: The Access Provider package relevant to your deployment.
-
Package name: PTKcpsdk.rte
-
Package subdirectory: /output-unix/AIX/PTKcpsdk
Note
ProtectToolkit C Runtime and ProtectToolkit C SDK cannot be installed concurrently. To switch from one package to the other, uninstall the package that is no longer required and then install the new one.
-